Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide vim with python support #429

Open
drscream opened this issue Nov 12, 2016 · 4 comments
Open

Provide vim with python support #429

drscream opened this issue Nov 12, 2016 · 4 comments

Comments

@drscream
Copy link

drscream commented Nov 12, 2016 •
edited
Loading

It would be nice to have a vim build with python support enabled especially on MacOSX. My recommended way would be an extra package called vim-nox which matches the naming on Debian and other distributions.

Description from vim-nox:

This package contains a version of vim compiled with support for
scripting with Lua, Perl, Python, Ruby, and Tcl but no GUI.

If you need more information let me know please.
wiedi pushed a commit to wiedi/pkgsrc-legacy that referenced this issue Nov 17, 2016
Updated py-oauth2client to 4.0.0.
ec03e3e 
## v4.0.0

New features:
* New Django samples. (#636)
* Add support for RFC7636 PKCE. (#588)
* Release as a universal wheel. (#665)

Bug fixes:
* Fix django authorization redirect by correctly checking validity of credentials. (#651)
* Correct query loss when using parse_qsl to dict. (#622)
* Switch django models from pickle to jsonpickle. (#614)
* Support new MIDDLEWARE Django 1.10 aetting. (#623)
* Remove usage of os.environ.setdefault. (#621)
* Handle missing storage files correctly. (#576)
* Try to revoke token with POST when getting a 405. (#662)

Internal changes:
* Use transport module for GCE environment check. (#612)
* Remove __author__ lines and add contributors.md. (#627)
* Clean up imports. (#625)
* Use transport.request in tests. (#607)
* Drop unittest2 dependency (#610)
* Remove backslash line continuations. (#608)
* Use transport helpers in system tests. (#606)
* Clean up usage of HTTP mocks in tests. (#605)
* Remove all uses of MagicMock. (#598)
* Migrate test runner to pytest. (TritonDataCenter#569)
* Merge util.py and _helpers.py. (#579)
* Remove httplib2 imports from non-transport modules. (#577)

Breaking changes:
* Drop Python 3.3 support. (#603)
* Drop Python 2.6 support. (#590)
* Remove multistore_file. (#589)

## v3.0.0

* Populate `token_expiry` for GCE credentials. (#473)
* Move GCE metadata interface to a separate module. (TritonDataCenter#520)
* Populate `scopes` for GCE credentials. (TritonDataCenter#524)
* Fix Python 3.5 compatibility. (TritonDataCenter#531)
* Add `oauth2client.contrib.sqlalchemy`, a SQLAlchemy-based credential store. (TritonDataCenter#527)
* Improve error when an invalid client secret is provided. (TritonDataCenter#530)
* Add `oauth2client.contrib.multiprocess_storage`. This supersedes the functionality in `oauth2client.contrib.multistore_file`. (TritonDataCenter#504)
* Pull httplib2 usage into a separate transport module. (TritonDataCenter#559, TritonDataCenter#561)
* Refactor all django-related code into `oauth2client.contrib.django_util`. Add `DjangoORMStorage`, remove `FlowField`. (TritonDataCenter#546)
* Fix application default credentials resolution order. (#570)
* Add configurable timeout for GCE metadata server check. (#571)
* Add warnings when using deprecated `approval_prompt='force'`. (#572)
* Add deprecation warning to `oauth2client.contrib.multistore_file`. (#574)
* (Hygiene) PEP8 compliance and various style fixes (TritonDataCenter#537, TritonDataCenter#540, TritonDataCenter#552, TritonDataCenter#562)
* (Hygiene) Remove duplicated exception classes in `oauth2client.contrib.appengine`. (TritonDataCenter#533)

NOTE: The next major release of oauth2client (v4.0.0) will remove the `oauth2client.contrib.multistore_file` module.

## v2.2.0

* Added support to override `token_uri` and `revoke_uri` in `oauth2client.service_account.ServiceAccountCredentials`. (TritonDataCenter#510)
* `oauth2client.contrib.multistore_file` now handles `OSError` in addition to `IOError` because Windows may raise `OSError` where other platforms will raise `IOError`.
* `oauth2client.contrib.django_util` and `oauth2client.contrib.django_orm` have been updated to support Django 1.8 - 1.10. Versions of Django below 1.8 will not work with these modules.

## v2.1.0

* Add basic support for JWT access credentials. (TritonDataCenter#503)
* Fix `oauth2client.client.DeviceFlowInfo` to use UTC instead of the system timezone when calculating code expiration.

## v2.0.2

* Fix issue where `flask_util.UserOAuth2.required` would accept expired credentials (TritonDataCenter#452).
* Fix issue where `flask_util` would fill the session with `Flow` objects (TritonDataCenter#498).
* Fix issue with Python 3 binary strings in `Flow.step2_exchange` (TritonDataCenter#446).
* Improve test coverage to 100%.

## v2.0.1

* Making scopes optional on Google Compute Engine `AppAssertionCredentials`
  and adding a warning that GCE won't honor scopes (TritonDataCenter#419)
* Adding common `sign_blob()` to service account types and a
  `service_account_email` property. (TritonDataCenter#421)
* Improving error message in P12 factory
  `ServiceAccountCredentials.from_p12_keyfile` when pyOpenSSL is
  missing. (TritonDataCenter#424)
* Allowing default flags in `oauth2client.tools.run_flow()`
  rather than forcing users to create a dummy argparser (TritonDataCenter#426)
* Removing `oauth2client.util.dict_to_tuple_key()` from public
  interface (TritonDataCenter#429)
* Adding `oauth2client.contrib._appengine_ndb` helper module
  for `oauth2client.contrib.appengine` and moving most code that
  uses the `ndb` library into the helper (TritonDataCenter#434)
* Fix error in `django_util` sample code (TritonDataCenter#438)

## v2.0.0-post1

* Fix Google Compute Engine breakage (TritonDataCenter#411, breakage introduced in TritonDataCenter#387) that
  made it impossible to obtain access tokens
* Implement `ServiceAccountCredentials.from_p12_keyfile_buffer()`
  to allow passing a file-like object in addition to the factory
  constructor that uses a filename directly (TritonDataCenter#413)
* Implement `ServiceAccountCredentials.create_delegated()`
  to allow upgrading a credential to one that acts on behalf
  of a given subject (TritonDataCenter#420)
@drscream
Copy link
Author

drscream commented Dec 8, 2016

I've created a package description for vim-nox in wip, maybe someone could have a look? https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=tree;f=vim-nox;h=31dd79c4ce901112ebccbc349cedf2571c7f6e41;hb=HEAD

jperkin referenced this issue in TritonDataCenter/pkgbuild Dec 16, 2016
joyent/pkgsrc#429 build vim with language support.
bf46a83
@jperkin
Copy link
Collaborator

jperkin commented Dec 16, 2016

There shouldn't be any need for a vim-nox package as the primary vim package is already explicitly build without X11 support (that is provided by vim-gtk* etc.)

I've enabled the languages support in the vim package and that should show up in the next build, though will be the same version so will need a re-install. I'll post when that build completes.

@drscream
Copy link
Author

Hello @jperkin thanks a lot for your reply, I only adapted the packages from other operating systems because maybe (for random reason, dependency reason) we would like to have a vim version without any scripting language support.

@jperkin
Copy link
Collaborator

jperkin commented Dec 19, 2016

Yeh I'd quite like to see that, vim-lite perhaps, or vim-tiny to match what Debian call it. Then we'd have:

  • vim: Non-X11, languages enabled
  • vim-gtk*: X11, languages enabled
  • vim-lite: Non-X11, languages disabled

That should cover all requirements. Do you want to have a go at creating that and I'll import it? Would be worth taking a look to see what else they do with the vim-tiny package to see if there's any other useful tweaks we can use. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jperkin @drscream