Heya!
I recently moved all the setup.py configuration into setup.cfg for
Pyroma. That worked very nicely. So I started doing it for my other
packages, but with svn.path I failed. Everything *looked* fine, and I
uploaded a 4.0 to PyPI, but if I install that in a virtualenv,
importing svg or svg.path fails. The Python installation can't find
them. Declaring them as a namespace means you can import them, but the
imports are empty, there is no attributes to the modules, so you still
can't use the package.
Is this possible? And if so, how?
Here's a link to the 4.0 release with all the info in the setup.cfg.
https://github.com/regebro/svg.path/tree/5f941b729f0b7e3991f238776c9391d579…
Hi, I am trying to use the technique of pillow to pre-emptively build windows 38 wheel for x_64 and also i686.
I used https://github.com/matthew-brett/multibuild/blob/devel/install_python.ps1 as a starting point, but made the
version stuff explicit so my install ps1 looks like
> # Install specified Python version.
> # Install only if:
> # Our current matrix entry uses this Python version AND
> # Python version is not already available.
> Write-Host "install_python.ps1 PYTHON=Python${env:PYVER}" -ForegroundColor Yellow
>
> $PYTHON="C:\Python${env:PYVER}"
> $py_exe = "${PYTHON}\Python.exe"
> Write-Host "py_exe: ${py_exe}" -ForegroundColor Yellow
>
> if ( [System.IO.File]::Exists($py_exe) ) {
> Write-Host "${py_exe} apparently exists" -ForegroundColor Red
> exit 0
> }
> if ($PYTHON -eq "C:\Python38-x64") {
> $exe_suffix="-amd64"
> $req_ver="3.8.0"
> $req_dir="3.8.0"
> } elseif ($PYTHON -eq "C:\Python38") {
> $exe_suffix=""
> $req_ver="3.8.0"
> $req_dir="3.8.0"
> } else {
> Write-Host "python undiscovered" -ForegroundColor Red
> exit 0
> }
>
> $py_url = "https://www.python.org/ftp/python"
> Write-Host "Installing Python ${req_ver}$exe_suffix..." -ForegroundColor Yellow
> $exePath = "$env:TEMP\python-${req_ver}${exe_suffix}.exe"
> $downloadFile = "$py_url/${req_dir}/python-${req_ver}${exe_suffix}.exe"
>
> Write-Host "exePath=${exePath} downloadFile=${downloadFile}"
>
> Write-Host "Downloading $downloadFile..."
> (New-Object Net.WebClient).DownloadFile($downloadFile, $exePath)
> Write-Host "Installing..."
> cmd /c start /wait $exePath /quiet TargetDir="$PYTHON" Shortcuts=0 Include_launcher=0 InstallLauncherAllUsers=0
> Write-Host "Python ${req_ver} installed to $PYTHON"
>
> echo "$(& $py_exe --version 2> $null)"
the appveyor log reoports this as working so there I see this reported
> install_python.ps1 PYTHON=Python38-x64
> py_exe: C:\Python38-x64\Python.exe
> Installing Python 3.8.0-amd64...
> exePath=C:\Users\appveyor\AppData\Local\Temp\1\python-3.8.0-amd64.exe downloadFile=https://www.python.org/ftp/python/3.8.0/python-3.8.0-amd64.exe
> Downloading https://www.python.org/ftp/python/3.8.0/python-3.8.0-amd64.exe...
> Installing...
> Python 3.8.0 installed to C:\Python38-x64
> Python 3.8.0
I then used this python to build a reportlab wheel; that was reported as
C:\projects\reportlab\dist\reportlab-3.5.32-cp38-cp38m-win_amd64.whl
I loaded this wheel onto a windows 10 machine which reports itself as 64-bit OS x64-based processor
I installed Python 3.8 and used it to create a virtualenv; the venv python reports itself as Python 3.8.0 (64-bit), but
when run it says Python 3.8.0 ........ [MSC v.1916 64 bit (AMD64)] on win32
The real problem is that the virtualenv pip wuill not install my wheel the error says
ERROR: reportlab-3.5.32-cp38-cp38m-win_amd64.whl is not a supported wheel on this platform.
I have already built reportlab-3.5.32-cp37-cp37m-win_amd64.whl as part of the standard appveyor process and that
installs fine into a virtualenv built for Python 3.7.5.
I am slightly mystified can anyone suggest what I am doing wrong?
--
Robin Becker
I've recently released version 0.3.0 of distlib on PyPI [1]. For newcomers,distlib is a library of packaging functionality which is intended to beusable as the basis for third-party packaging tools.
The main changes in this release are as follows:
* Partially addressed #102: modules attribute of InstalledDistribution was incorrectly computed as a list of bytes, rather than a list of str. This has now been corrected.
* Updated Locator._get_digest to check PyPI JSON responses for a "digests" dictionary before trying "algo_digest" keys. Thanks to Jeffery To for the patch.
* Fixed #123: Improved error message if a resource isn't found.
* Fixed #124: Stopped norm-casing the executable written into shebangs, as it doesn't work for some non-ASCII paths.
* Fixed #125: Updated launchers with versions that correctly report errors containing non-ASCII characters. The updated launchers now also support relative paths (see http://bit.ly/2JxmOoi for more information).
* Fixed #127: Allowed hyphens in flags in export specifications.
* Changed Python version handling to accommodate versions like e.g. 3.10 (no longer assume a version X.Y where X and Y are single digits).
A more detailed change log is available at [2].
Please try it out, and if you find any problems or have any suggestions for improvements,please give some feedback using the issue tracker! [3]
Regards,
Vinay Sajip
[1] https://pypi.org/project/distlib/0.3.0/[2]https://distlib.readthedocs.io/en/0.3.0/[3]https://bitbucket.org/pypa/distlib/issues/new
There's a pull request against wheel that I feel out of my depth
reviewing: https://github.com/pypa/wheel/pull/314
I'm looking for anyone with experience on macOS binary compatibility to
help validate the solution. Help is really appreciated!
Hello everyone!
On behalf of the PyPA, I am pleased to announce that pip 19.3 has been
released.
The full release notes are available at https://pip.pypa.io/en/stable/news/
but the main highlights are:
- support for `manylinux2014` wheels
- slightly faster load time
- many bug fixes and lots of minor improvements
While the upgrade should be painless, we would recommend that users test
the release before deploying in production, as with any other software
release.
To install pip 19.3, you can use `get-pip.py` (as described in
https://pip.pypa.io/en/latest/installing) or run:
`python -m pip install --upgrade pip`
Note that if you are using a version of pip supplied by your distribution
vendor, vendor-supplied upgrades will be available in due course.
The pip development team is extremely grateful to everyone in the community
for their contributions. Thanks to everyone who put so much effort into the
new release.
Many of the contributions came from community members, whether in the form
of code, participation in design discussions and/or bug reports.
Hello all.
I recently went through the packaging exercise that's documented here:
https://packaging.python.org/tutorials/packaging-projects/
Everything seemed to work fine until I got to the testing step where I
was supposed to do an "import example_pkg". Python said it was unable
to find the package. My user name on the test PyPI site is dcoup, so I
also tried "import example_pkg_dcoup", but that didn't work either. I
was using a virtual environment, as recommended in the tutorial. I also
tried the installation and test outside of the virtual environment, but
that didn't work either.
In my case I'm using my Windows 10 workstation. I'm attaching a file
with the output of several commands that might help. Is there something
I'm missing?
Regards,
Douglas Coup
--
Objective Systems, Inc.
REAL WORLD ASN.1 AND XML SOLUTIONS
Tel: +1 (484) 875-9841
Fax: +1 (484) 875-9830
Toll-free: (877) 307-6855 (USA only)
http://www.obj-sys.com
Hi,
I am a beginner, don't know if pip installed in my laptop...
Can you tell me how to download pip? my current version of python is 3.7.4.
Thanks.
Hao
Hi,
We are testing team working on Smart Metering Implementation Programme and use pySerial 2.7. Our IT team is preparing an OS build with all the required tools in it. To silently install the tool they them in MSI. I was wondering if you have this in MSI format and can share it with us?
Looking forward to your reply.
Regards
Saqib Rashid
This electronic message contains information from Telef?nica UK Limited which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email. Switchboard: +44 (0)113 272 2000 Contact: www.o2.co.uk/contactus Telef?nica UK Limited, 260 Bath Road, Slough, Berkshire SL1 4DX. Registered in England and Wales: 1743099. VAT number: GB 778 6037 85
